feat(backend): add weighted fair job queue with priority scheduling#648
Conversation
Introduce WFQ scheduler across critical/high/normal/low priority classes, BullMQ-backed persistence, billing job worker integration, and Prometheus queue metrics to keep time-sensitive jobs ahead of analytics under load.
|
@od-hunter Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Integrate Smartdevs17/main into feature/weighted-fair-job-queue, keeping WFQ queue infrastructure while adopting upstream MV refresh views and pg dependency.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 34266369 | Triggered | Generic Password | e40c64a | backend/config/tests/redis.test.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Closes #597